While preparing Master Data Repository, the first task is to identify the data stores in the application that need to be kept consistent through regular data synchronization. For example, organization A and organization B are merged and you wish to integrate supplier information of both the organizations. Each data source that you identify for organization A and organization B will form a spoke in the hub-and-spoke MDM model of Process Platform.

After identifying the data sources, the next step is to identify the entities from each data sources for integration. Here, the term entity refers to a representation of relevant information about a business object, expressed in the form of an XML Schema. For a database, the entity is a database table - this can be expressed as an XML definition. For an external Web service, the schema of the data that the service provides becomes the entity definition.

In the above stated example, the supplier data in both the organizations is described in terms of a database entity with appropriate attribute names and data types. The Supplier database entity is expressed in the form of an XML-based schema description.

MDM stores the related content in the MDM repository tables which are named as RCOR(Relational Common Object Repository) tables. If the tables are shared by all the spokes and hub, then the model is called as central repository. If the RCOR tables are created for both hub and spokes separately, then the model is a distributed one. For more information on configuring distributed and central repositories, refer to Configuring an MDM Repository.

Similar to the RCOR tables there are RCOR fields which contain MDM related information. These RCOR fields must be added to each data entity(table in the hub database) in the master data repository(hub).

1. Preparing master data repository:
   
   1. Determine the schema for the data entities that are part of the master data repository. If you are using an existing data repository as the master data repository, modify the data entities in the data repository to match this schema. Else, create a new data repository in DB2, Oracle, MS SQL, or MySQL data repository server.
      
   2. If you are using an existing data repository as the master data repository, add the RCOR fields to each data entity in the repository. Refer to MDM Specific Fields for details.

      Note:
      If you are using the State Models, adding the RCOR fields to the hub data entities is not required.

      
      
   3. Run the database scripts in the master data repository to create some required procedures. The database scripts are available in the <Process_Platform_Installation_Directory>/<Instance name>/components/mdm/dbscripts/application folder of the server where Process Platform is installed. Execute the following files depending on your database:

      If the database is...	Then
      Oracle	Run the script MDM_ORACLE.sql
      MS SQL	Run the script MDM_SQLSERVER.sql
      MySQL	Run the script MDM_MySQL.sql
      DB2	Run the script MDM_DB2.sql

      For information on running the scripts, refer to the database vendor documentation. The application data stores are now ready for integration.
      
      
2. Creating MDM Repository Tables:
   
   1. While installing MDM ISV(This is installed with Process Platform), MDM Repository Tables will be created with the specified database configuration. In case, if it is required to create MDM Repository Tables separately then you can run the appropriate scripts from the table given below. The scripts are available in the folder <Process_Platform_Installation_Directory>/<Instance name>/components/mdm/dbscripts/repository of the computer where Process Platform is installed. For information on running the scripts, refer to the database vendor documentation.

      If the database is...	Then...
      Oracle	Run the following scripts: 1. MDM_ORACLE_TABLES.sql 2. MDM_ORACLE_TRIGGERS.sql 3. MDM_INIT
      MS SQL	Run the following scripts: 1. MDM_SQLSERVER_TABLES.sql 2. MDM_SQLSERVER_TRIGGERS.sql 3. MDM_INIT
      MySQL	Run the following scripts: 1. MDM_MySQL_TABLES.sql 2. MDM_MySQL_TRIGGERS.sql 3. MDM_INIT
      DB2	Run the following scripts: 1. MDM_DB2_TABLES.sql 2. MDM_DB2_TRIGGERS.sql 3. MDM_INIT